Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80d2ef079cbb4ee6fbabc829d12ae2d006084948cf376715bdec161cff0b4294

Tx prefix hash: 09a341a97cbd1d277335edbfaca193d9a43fa04a8019139e8ea61bea64ab678b
Tx public key: 12901e8828c38c84dc1aa6aa8ae3e9b9c279ddec19740f9d6d0edbc1e7f24094
Timestamp: 1580113986 Timestamp [UCT]: 2020-01-27 08:33:06 Age [y:d:h:m:s]: 05:141:18:11:36
Block: 53721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1252234 RingCT/type: yes/0
Extra: 0112901e8828c38c84dc1aa6aa8ae3e9b9c279ddec19740f9d6d0edbc1e7f2409402110000000249b77a3d000000000000000000

1 output(s) for total of 407.403798770000 dcy

stealth address amount amount idx
00: 8e51f1d913ee41e22609eae6cc2c7029f2b574cb1376a49ff875a23b0982b113 407.403798770000 99593 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": 53731, "vin": [ { "gen": { "height": 53721 } } ], "vout": [ { "amount": 407403798770, "target": { "key": "8e51f1d913ee41e22609eae6cc2c7029f2b574cb1376a49ff875a23b0982b113" } } ], "extra": [ 1, 18, 144, 30, 136, 40, 195, 140, 132, 220, 26, 166, 170, 138, 227, 233, 185, 194, 121, 221, 236, 25, 116, 15, 157, 109, 14, 219, 193, 231, 242, 64, 148, 2, 17, 0, 0, 0, 2, 73, 183, 122, 61, 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