Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3741539f3d6f03647763f10ece2f6a9ea0c381d84d2a10fdc78b8a0ba312bfea

Tx prefix hash: 04d56918828a47f4be78f9992b161940ccc2cbc031988a04dc04689bb1878ce7
Tx public key: f04974980c461f45484fc34e24103d207cab1185f1da2f15f89fcbfd77b2b79c
Timestamp: 1589363535 Timestamp [UCT]: 2020-05-13 09:52:15 Age [y:d:h:m:s]: 04:352:02:18:53
Block: 100472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171537 RingCT/type: yes/0
Extra: 01f04974980c461f45484fc34e24103d207cab1185f1da2f15f89fcbfd77b2b79c02110000043960e3cc90000000000000000000

1 output(s) for total of 285.164406684000 dcy

stealth address amount amount idx
00: 4c7043d352579cffd550b78c23bbe97fcb6e71b5d3a1c491f7309a7ac9158bb2 285.164406684000 177012 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": 100482, "vin": [ { "gen": { "height": 100472 } } ], "vout": [ { "amount": 285164406684, "target": { "key": "4c7043d352579cffd550b78c23bbe97fcb6e71b5d3a1c491f7309a7ac9158bb2" } } ], "extra": [ 1, 240, 73, 116, 152, 12, 70, 31, 69, 72, 79, 195, 78, 36, 16, 61, 32, 124, 171, 17, 133, 241, 218, 47, 21, 248, 159, 203, 253, 119, 178, 183, 156, 2, 17, 0, 0, 4, 57, 96, 227, 204, 144, 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