Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7f273cf36c5805191359dbe0647a3aa43d19dc1ec9f1a5a67498bf457380b2

Tx prefix hash: bcaed1cb1262c620765ed583d7a2a9f55910e628de6994d2f3400620b1da9380
Tx public key: 4708e3b41788b50305511d0b6849348212194eee7e8a49438ce9b6376816c6dc
Timestamp: 1582384408 Timestamp [UCT]: 2020-02-22 15:13:28 Age [y:d:h:m:s]: 05:011:15:22:56
Block: 70250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161522 RingCT/type: yes/0
Extra: 014708e3b41788b50305511d0b6849348212194eee7e8a49438ce9b6376816c6dc021100000001c71d3ff9000000000000000000

1 output(s) for total of 359.114872202000 dcy

stealth address amount amount idx
00: a668040ccad7a936288d0f1132318a648eab9e383979039d553ac6c78b901370 359.114872202000 129743 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": 70260, "vin": [ { "gen": { "height": 70250 } } ], "vout": [ { "amount": 359114872202, "target": { "key": "a668040ccad7a936288d0f1132318a648eab9e383979039d553ac6c78b901370" } } ], "extra": [ 1, 71, 8, 227, 180, 23, 136, 181, 3, 5, 81, 29, 11, 104, 73, 52, 130, 18, 25, 78, 238, 126, 138, 73, 67, 140, 233, 182, 55, 104, 22, 198, 220, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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