Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 280a21e146703990e769c54f07560f5cf8d7ea08d64a7a8ed4e57336aa47d7de

Tx prefix hash: a9605e04c3ee39d62dd0ccfb44877ace9dfb94a8fa8f0618d0828fead2e753a9
Tx public key: 40f6088ff213eb39a61fb1129a08b74f177cf043820e28832be19ba6ae92d31e
Timestamp: 1676363205 Timestamp [UCT]: 2023-02-14 08:26:45 Age [y:d:h:m:s]: 01:332:20:55:40
Block: 696673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498852 RingCT/type: yes/0
Extra: 0140f6088ff213eb39a61fb1129a08b74f177cf043820e28832be19ba6ae92d31e02110000000233af99f4000000000000000000

1 output(s) for total of 3.017401254000 dcy

stealth address amount amount idx
00: 386886fac9e6e1572a85b3075f3af3c0e4371a89bdc4521be43e50e69dfe8d28 3.017401254000 1139714 of 0

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": 696683, "vin": [ { "gen": { "height": 696673 } } ], "vout": [ { "amount": 3017401254, "target": { "key": "386886fac9e6e1572a85b3075f3af3c0e4371a89bdc4521be43e50e69dfe8d28" } } ], "extra": [ 1, 64, 246, 8, 143, 242, 19, 235, 57, 166, 31, 177, 18, 154, 8, 183, 79, 23, 124, 240, 67, 130, 14, 40, 131, 43, 225, 155, 166, 174, 146, 211, 30, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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