Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cee06daffafe323d148f15dff62b6acc35327b63be41f2431b5d4a47c6816239

Tx prefix hash: eda39a0072ca0fc1a011e1f4dd6999a3e314381849915c559ba599f4eb8342c3
Tx public key: fc8fbfb2e985faea4d2bb545f9dc4a23c77a2664f16ad91b3b20c3df35691259
Timestamp: 1621750006 Timestamp [UCT]: 2021-05-23 06:06:46 Age [y:d:h:m:s]: 04:024:23:52:35
Block: 265467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1040584 RingCT/type: yes/0
Extra: 01fc8fbfb2e985faea4d2bb545f9dc4a23c77a2664f16ad91b3b20c3df3569125902110000000b0bb79a4a000000000000000000

1 output(s) for total of 80.983803263000 dcy

stealth address amount amount idx
00: 08fcafd5aae5aeba2f56f5480e2060feae6c15eb7301ea96bca87ee5a197af91 80.983803263000 557973 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": 265477, "vin": [ { "gen": { "height": 265467 } } ], "vout": [ { "amount": 80983803263, "target": { "key": "08fcafd5aae5aeba2f56f5480e2060feae6c15eb7301ea96bca87ee5a197af91" } } ], "extra": [ 1, 252, 143, 191, 178, 233, 133, 250, 234, 77, 43, 181, 69, 249, 220, 74, 35, 199, 122, 38, 100, 241, 106, 217, 27, 59, 32, 195, 223, 53, 105, 18, 89, 2, 17, 0, 0, 0, 11, 11, 183, 154, 74, 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