Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96d07f205b5ee586ae6e6dfdd698216d92222425cec058bf2f700a1e9af0a4d3

Tx prefix hash: d1effcd06e152744f4eb78d4d807a8be8b642623e88f2d05464145860f76f7bb
Tx public key: 24a6f4835317330d8a85dcdaa7dc5455d95ee85d62c392ecf3fbdcb87674518b
Timestamp: 1765950411 Timestamp [UCT]: 2025-12-17 05:46:51 Age [y:d:h:m:s]: 00:006:08:45:11
Block: 1435365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4555 RingCT/type: yes/0
Extra: 0124a6f4835317330d8a85dcdaa7dc5455d95ee85d62c392ecf3fbdcb87674518b021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11942c338eabd44b62e109f959d0924f854b703636e63a60ad1e6fb6d44b3e49 0.600000000000 1924162 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": 1435375, "vin": [ { "gen": { "height": 1435365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11942c338eabd44b62e109f959d0924f854b703636e63a60ad1e6fb6d44b3e49" } } ], "extra": [ 1, 36, 166, 244, 131, 83, 23, 51, 13, 138, 133, 220, 218, 167, 220, 84, 85, 217, 94, 232, 93, 98, 195, 146, 236, 243, 251, 220, 184, 118, 116, 81, 139, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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