Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2da000e20cd3d46d6b7ce197466c90e35c5b27f42fc07038b0b58895ec548c4c

Tx prefix hash: 12e91a5ceafbcb1e0a8e5d03ba3c92b8a2733f45c3a7d54104f57c9666904d1b
Tx public key: c676771bcf3ff75c8e07e06c75d3f8b06f19c4f5e4932d1ff28ddb6a5d0c9788
Timestamp: 1580702918 Timestamp [UCT]: 2020-02-03 04:08:38 Age [y:d:h:m:s]: 05:098:03:25:40
Block: 57710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1222022 RingCT/type: yes/0
Extra: 01c676771bcf3ff75c8e07e06c75d3f8b06f19c4f5e4932d1ff28ddb6a5d0c9788021100000004bd0f9f9f000000000000000000

1 output(s) for total of 395.169698054000 dcy

stealth address amount amount idx
00: da1acf05dda4f18a189eaafdb1b1955e70974fc83567b3684ec1a5c352a33678 395.169698054000 106652 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": 57720, "vin": [ { "gen": { "height": 57710 } } ], "vout": [ { "amount": 395169698054, "target": { "key": "da1acf05dda4f18a189eaafdb1b1955e70974fc83567b3684ec1a5c352a33678" } } ], "extra": [ 1, 198, 118, 119, 27, 207, 63, 247, 92, 142, 7, 224, 108, 117, 211, 248, 176, 111, 25, 196, 245, 228, 147, 45, 31, 242, 141, 219, 106, 93, 12, 151, 136, 2, 17, 0, 0, 0, 4, 189, 15, 159, 159, 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