Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 134592ec4de58895db2b65c412914be94b0e0772124d981a366050fb7cef5c2d

Tx prefix hash: fbb0879e8b911be1618495171ec5d94a40594780b4dfd8decfdc14b682a23e0c
Tx public key: d00432aa14bf3c60ebbd7e729312d6d09c5162bd33fc6e4fdbe767712d6b5458
Timestamp: 1699915272 Timestamp [UCT]: 2023-11-13 22:41:12 Age [y:d:h:m:s]: 01:142:03:08:20
Block: 891049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362746 RingCT/type: yes/0
Extra: 01d00432aa14bf3c60ebbd7e729312d6d09c5162bd33fc6e4fdbe767712d6b545802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.684833139000 dcy

stealth address amount amount idx
00: eadd27f735a30a471e047a5be24da2a235b275763e33d6e6a762a6ccf279b562 0.684833139000 1347084 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": 891059, "vin": [ { "gen": { "height": 891049 } } ], "vout": [ { "amount": 684833139, "target": { "key": "eadd27f735a30a471e047a5be24da2a235b275763e33d6e6a762a6ccf279b562" } } ], "extra": [ 1, 208, 4, 50, 170, 20, 191, 60, 96, 235, 189, 126, 114, 147, 18, 214, 208, 156, 81, 98, 189, 51, 252, 110, 79, 219, 231, 103, 113, 45, 107, 84, 88, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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