Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae2c0b79e7de9c437cc0271b529b506e0af81c003e0bf42817c8ebac894d0f51

Tx prefix hash: 2fe0d775c44b98b165a77ba799905bb0296df2a53ce5f452d08bac0c28145694
Tx public key: 54be7fe8e2c6ef26a881b96660bed2a7a33adba2da240ef812d938f4bd7af8c4
Timestamp: 1720890572 Timestamp [UCT]: 2024-07-13 17:09:32 Age [y:d:h:m:s]: 00:260:17:55:39
Block: 1064953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186269 RingCT/type: yes/0
Extra: 0154be7fe8e2c6ef26a881b96660bed2a7a33adba2da240ef812d938f4bd7af8c402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 923b3a0122ff075c59364136f8f53f8060fb31d634c47d6ef30736b53f231f34 0.600000000000 1535494 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": 1064963, "vin": [ { "gen": { "height": 1064953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "923b3a0122ff075c59364136f8f53f8060fb31d634c47d6ef30736b53f231f34" } } ], "extra": [ 1, 84, 190, 127, 232, 226, 198, 239, 38, 168, 129, 185, 102, 96, 190, 210, 167, 163, 58, 219, 162, 218, 36, 14, 248, 18, 217, 56, 244, 189, 122, 248, 196, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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