Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3b4f78c5d8fe510334c0c607492975ca2d0c007a348b875f5b22829feac3c33

Tx prefix hash: ac791f212df3c6541519d8546ca3225cc70d7b374fd2b6f00b6bc98eed470499
Tx public key: a68dbff8e8cec8ad4a9e7a2fa44fccc606033036561bccd8ed4e8be18251e458
Timestamp: 1729357944 Timestamp [UCT]: 2024-10-19 17:12:24 Age [y:d:h:m:s]: 00:234:01:45:31
Block: 1135130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167120 RingCT/type: yes/0
Extra: 01a68dbff8e8cec8ad4a9e7a2fa44fccc606033036561bccd8ed4e8be18251e45802110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fbd595d06f387d473f1ebc26fd30bc5051ca5ead8b7730cf103711232d6c9db 0.600000000000 1618461 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": 1135140, "vin": [ { "gen": { "height": 1135130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fbd595d06f387d473f1ebc26fd30bc5051ca5ead8b7730cf103711232d6c9db" } } ], "extra": [ 1, 166, 141, 191, 248, 232, 206, 200, 173, 74, 158, 122, 47, 164, 79, 204, 198, 6, 3, 48, 54, 86, 27, 204, 216, 237, 78, 139, 225, 130, 81, 228, 88, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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