Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8567f4185afcdccd1b5e735d6058a063da7194905f84a4d63f9215124489ab93

Tx prefix hash: ad897a1c24b6703c51af2a5f8f344ff1ca2a4d394d062f58af26cd28f9f8b63b
Tx public key: b821e16e799170ff9a66fb941df076bbc0d9c1af28c68930089856dd2b0486ec
Timestamp: 1734911202 Timestamp [UCT]: 2024-12-22 23:46:42 Age [y:d:h:m:s]: 00:091:02:53:21
Block: 1181092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64863 RingCT/type: yes/0
Extra: 01b821e16e799170ff9a66fb941df076bbc0d9c1af28c68930089856dd2b0486ec0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a049c892372fc74d3a4ea08247a2ead83e51b74ec7520b068c86a346dbe8b6b9 0.600000000000 1667507 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1181102, "vin": [ { "gen": { "height": 1181092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a049c892372fc74d3a4ea08247a2ead83e51b74ec7520b068c86a346dbe8b6b9" } } ], "extra": [ 1, 184, 33, 225, 110, 121, 145, 112, 255, 154, 102, 251, 148, 29, 240, 118, 187, 192, 217, 193, 175, 40, 198, 137, 48, 8, 152, 86, 221, 43, 4, 134, 236, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8