Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeeaf19757e0a4fa8bd8a84180e5f0ef1fd2ee1be33e6ba7d859ee742f0a281c

Tx prefix hash: 5c3bbea1122aa204eb78bbbae7abe580cfdaad6ffd7390262e111878cdd032a9
Tx public key: 1b4cbd64364c39ccc8aadb72837330f770531026af0b1a5964c2c29b2de4c026
Timestamp: 1726381262 Timestamp [UCT]: 2024-09-15 06:21:02 Age [y:d:h:m:s]: 00:117:09:07:52
Block: 1110458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83942 RingCT/type: yes/0
Extra: 011b4cbd64364c39ccc8aadb72837330f770531026af0b1a5964c2c29b2de4c026021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d49100cb597628d4951f4dc2b0de101ef0de08cd29e8c32eca416a12f37169c 0.600000000000 1589071 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": 1110468, "vin": [ { "gen": { "height": 1110458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d49100cb597628d4951f4dc2b0de101ef0de08cd29e8c32eca416a12f37169c" } } ], "extra": [ 1, 27, 76, 189, 100, 54, 76, 57, 204, 200, 170, 219, 114, 131, 115, 48, 247, 112, 83, 16, 38, 175, 11, 26, 89, 100, 194, 194, 155, 45, 228, 192, 38, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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