Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 619e0c95c2534d6b38d21b4b7b1be5b5e1df6404e6cb180526eedc2a8d7e101c

Tx prefix hash: 8da2b191881d6743e7272db8c1de212cbb85362a233ee4f70df6d53427163ed9
Tx public key: e3d8aa814522990bba6d515845f834f6cc21b3dd2ac3827b82234f911c159ded
Timestamp: 1723384949 Timestamp [UCT]: 2024-08-11 14:02:29 Age [y:d:h:m:s]: 00:237:13:44:55
Block: 1085622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169670 RingCT/type: yes/0
Extra: 01e3d8aa814522990bba6d515845f834f6cc21b3dd2ac3827b82234f911c159ded021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72ec55d2b17151961763d9d6709f6f01fde358780f039adae416d4f397bba593 0.600000000000 1560209 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": 1085632, "vin": [ { "gen": { "height": 1085622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72ec55d2b17151961763d9d6709f6f01fde358780f039adae416d4f397bba593" } } ], "extra": [ 1, 227, 216, 170, 129, 69, 34, 153, 11, 186, 109, 81, 88, 69, 248, 52, 246, 204, 33, 179, 221, 42, 195, 130, 123, 130, 35, 79, 145, 28, 21, 157, 237, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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