Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74b56d1c2fad19cdebebfe8b93a319b13647da0f35adee08109fdb8b07227680

Tx prefix hash: cadf2aa0d6e9a16e45c84b2ee9f3f873451e86026e1a1397abd3f96444fc79a3
Tx public key: e60ae5d7edc49bc25f53157c98ecece0772de5d6816b2c3710b4724db9c8d002
Timestamp: 1578427178 Timestamp [UCT]: 2020-01-07 19:59:38 Age [y:d:h:m:s]: 05:067:11:11:00
Block: 40746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198209 RingCT/type: yes/0
Extra: 01e60ae5d7edc49bc25f53157c98ecece0772de5d6816b2c3710b4724db9c8d00202110000000ad81c26c0000000000000000000

1 output(s) for total of 449.781759259000 dcy

stealth address amount amount idx
00: 8ad2bb4e97a7ae686038a56a8d07c7d8989fd24bb3e5f33f6095357e31f25d63 449.781759259000 71848 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": 40756, "vin": [ { "gen": { "height": 40746 } } ], "vout": [ { "amount": 449781759259, "target": { "key": "8ad2bb4e97a7ae686038a56a8d07c7d8989fd24bb3e5f33f6095357e31f25d63" } } ], "extra": [ 1, 230, 10, 229, 215, 237, 196, 155, 194, 95, 83, 21, 124, 152, 236, 236, 224, 119, 45, 229, 214, 129, 107, 44, 55, 16, 180, 114, 77, 185, 200, 208, 2, 2, 17, 0, 0, 0, 10, 216, 28, 38, 192, 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