Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8694ebd59ca7be7733dfbd1556a144013df55f6ebfb7488274849d0ce50b66c

Tx prefix hash: 3dc69b819dc0bb2a29ecd4ae5a112516a7f6737319c20aa0e22bbb0cfe93ddaa
Tx public key: 59e3694e95d6b3e779e959bec2c3578bd44f6f28062467da7d8c6811ab31f041
Timestamp: 1742185189 Timestamp [UCT]: 2025-03-17 04:19:49 Age [y:d:h:m:s]: 00:298:04:07:43
Block: 1241017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210911 RingCT/type: yes/0
Extra: 0159e3694e95d6b3e779e959bec2c3578bd44f6f28062467da7d8c6811ab31f041021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aee552a3f83129e788cb76f4c3438b6f2874589c1d86112dcf5fa974ca17e4e6 0.600000000000 1727990 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": 1241027, "vin": [ { "gen": { "height": 1241017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aee552a3f83129e788cb76f4c3438b6f2874589c1d86112dcf5fa974ca17e4e6" } } ], "extra": [ 1, 89, 227, 105, 78, 149, 214, 179, 231, 121, 233, 89, 190, 194, 195, 87, 139, 212, 79, 111, 40, 6, 36, 103, 218, 125, 140, 104, 17, 171, 49, 240, 65, 2, 17, 0, 0, 0, 4, 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