Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e63e9e98b5f659925ebc5e7972ea65d81b92498632eb899a2bf6e96a1135205a

Tx prefix hash: ded25e3dab8ef3247e3571999f261399938df5119f9478d0bc742d21682b5f53
Tx public key: cf250e6933643dca47a868e133b3215bc6aa9d660c7b300c3d08b09f8f42a9da
Timestamp: 1736366369 Timestamp [UCT]: 2025-01-08 19:59:29 Age [y:d:h:m:s]: 00:305:19:38:58
Block: 1193105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216073 RingCT/type: yes/0
Extra: 01cf250e6933643dca47a868e133b3215bc6aa9d660c7b300c3d08b09f8f42a9da021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b66a5a0b6bdecbc5c6860ad954ed49064c8b432b05faf0dc4f9a078cacbf0e 0.600000000000 1679664 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": 1193115, "vin": [ { "gen": { "height": 1193105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b66a5a0b6bdecbc5c6860ad954ed49064c8b432b05faf0dc4f9a078cacbf0e" } } ], "extra": [ 1, 207, 37, 14, 105, 51, 100, 61, 202, 71, 168, 104, 225, 51, 179, 33, 91, 198, 170, 157, 102, 12, 123, 48, 12, 61, 8, 176, 159, 143, 66, 169, 218, 2, 17, 0, 0, 0, 6, 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