Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c729f7a90f7e7e15469315dcf7f2e86a1a1196c7d06cc51ecbf841a350afd57e

Tx prefix hash: 0587be61ca4228ee873bd0fe974aebcb939453200bfc05945862e10b2834ae74
Tx public key: e2c732583f524c23705154988fcb2f483fe15dd7067a9e8850d4b9419c90154f
Timestamp: 1577902325 Timestamp [UCT]: 2020-01-01 18:12:05 Age [y:d:h:m:s]: 05:015:14:08:21
Block: 36502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161254 RingCT/type: yes/0
Extra: 01e2c732583f524c23705154988fcb2f483fe15dd7067a9e8850d4b9419c90154f0211000000074ac5aa02000000000000000000

1 output(s) for total of 464.573650536000 dcy

stealth address amount amount idx
00: c0a9811bfa297aa33c1574f79867e62b0d2a2af2f4233f3777e1de0c3f9cfd70 464.573650536000 61860 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": 36512, "vin": [ { "gen": { "height": 36502 } } ], "vout": [ { "amount": 464573650536, "target": { "key": "c0a9811bfa297aa33c1574f79867e62b0d2a2af2f4233f3777e1de0c3f9cfd70" } } ], "extra": [ 1, 226, 199, 50, 88, 63, 82, 76, 35, 112, 81, 84, 152, 143, 203, 47, 72, 63, 225, 93, 215, 6, 122, 158, 136, 80, 212, 185, 65, 156, 144, 21, 79, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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