Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b56d4a53e526f213c6505be2595c3eb3af1f6127d965c7cbe9a4e98489725248

Tx prefix hash: bfb14cd709ad7a86cbbcb8e0b3ef5c62d2892a980a239e8960675a3ef0de437e
Tx public key: de7c302214a4f3c23dc0a32db897651abb25006242ab7872816ea7777c158361
Timestamp: 1578817520 Timestamp [UCT]: 2020-01-12 08:25:20 Age [y:d:h:m:s]: 05:043:10:23:28
Block: 43765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181204 RingCT/type: yes/0
Extra: 01de7c302214a4f3c23dc0a32db897651abb25006242ab7872816ea7777c15836102110000000b8a2ee0d9000000000000000000

1 output(s) for total of 439.538294845000 dcy

stealth address amount amount idx
00: 9d6756bd441a035b9504f15ea7f4b24a9adca8a71a28e1c05984aedff8321331 439.538294845000 79396 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": 43775, "vin": [ { "gen": { "height": 43765 } } ], "vout": [ { "amount": 439538294845, "target": { "key": "9d6756bd441a035b9504f15ea7f4b24a9adca8a71a28e1c05984aedff8321331" } } ], "extra": [ 1, 222, 124, 48, 34, 20, 164, 243, 194, 61, 192, 163, 45, 184, 151, 101, 26, 187, 37, 0, 98, 66, 171, 120, 114, 129, 110, 167, 119, 124, 21, 131, 97, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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