Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94fdab78e090a04db22bdc01a27ac239fc2dcd5d61c27f70d22b88d14587a6cb

Tx prefix hash: 943b26391365ab7b3591e36523b614639ab9cf3a06cb651b663090b106e4ea47
Tx public key: fd92ee6039f28c0288b4a13d4b9d30686ec5d012ef38c18fe7868d79b062225c
Timestamp: 1705810231 Timestamp [UCT]: 2024-01-21 04:10:31 Age [y:d:h:m:s]: 01:148:02:03:26
Block: 939877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366885 RingCT/type: yes/0
Extra: 01fd92ee6039f28c0288b4a13d4b9d30686ec5d012ef38c18fe7868d79b062225c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e843943bf052f43ccb7e52aed5814143d3a95c5b7a30b06db7d3b9a097cbac00 0.600000000000 1398011 of 15

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": 939887, "vin": [ { "gen": { "height": 939877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e843943bf052f43ccb7e52aed5814143d3a95c5b7a30b06db7d3b9a097cbac00" } } ], "extra": [ 1, 253, 146, 238, 96, 57, 242, 140, 2, 136, 180, 161, 61, 75, 157, 48, 104, 110, 197, 208, 18, 239, 56, 193, 143, 231, 134, 141, 121, 176, 98, 34, 92, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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