Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e26cc8d3ebe2742e0e8346a06d80a5c822d753c8e03c558865c6d22c8d5ed1a4

Tx prefix hash: 501b52d9c82274f1be3f70d8d05d1db555e6f9ea71f29974d444a4ff39b0aeff
Tx public key: cc62e68a2f5c630392a7db088aa4847644b8c5f40599eaaf889c6d79354ea668
Timestamp: 1578761614 Timestamp [UCT]: 2020-01-11 16:53:34 Age [y:d:h:m:s]: 05:298:13:31:46
Block: 43336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1361267 RingCT/type: yes/0
Extra: 01cc62e68a2f5c630392a7db088aa4847644b8c5f40599eaaf889c6d79354ea6680211000000054943cd9f000000000000000000

1 output(s) for total of 440.976855715000 dcy

stealth address amount amount idx
00: 4a13827fbf04a01e697c25a594eea099f94600108e3bf9150ee419372cd7c840 440.976855715000 78449 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": 43346, "vin": [ { "gen": { "height": 43336 } } ], "vout": [ { "amount": 440976855715, "target": { "key": "4a13827fbf04a01e697c25a594eea099f94600108e3bf9150ee419372cd7c840" } } ], "extra": [ 1, 204, 98, 230, 138, 47, 92, 99, 3, 146, 167, 219, 8, 138, 164, 132, 118, 68, 184, 197, 244, 5, 153, 234, 175, 136, 156, 109, 121, 53, 78, 166, 104, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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