Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e66b04fab9560b6a97fcb3f7f5595d68061a4bf65c0891e457fa6f975f25c30f

Tx prefix hash: 5facccd188a4f89d3b6f0ee3c7e3008820cc4a44ea4e0ecd9d9e387f6fd98641
Tx public key: e0bb36added37005cab8d90ef1ae3b80cb73e68a4de81269e3bae1ba7fad7f0d
Timestamp: 1741253633 Timestamp [UCT]: 2025-03-06 09:33:53 Age [y:d:h:m:s]: 00:260:06:49:46
Block: 1233303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183758 RingCT/type: yes/0
Extra: 01e0bb36added37005cab8d90ef1ae3b80cb73e68a4de81269e3bae1ba7fad7f0d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 803558d47553958b4b95b703daae8a010743a6b423d200607f6f8ff67dee8c58 0.600000000000 1720222 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": 1233313, "vin": [ { "gen": { "height": 1233303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803558d47553958b4b95b703daae8a010743a6b423d200607f6f8ff67dee8c58" } } ], "extra": [ 1, 224, 187, 54, 173, 222, 211, 112, 5, 202, 184, 217, 14, 241, 174, 59, 128, 203, 115, 230, 138, 77, 232, 18, 105, 227, 186, 225, 186, 127, 173, 127, 13, 2, 17, 0, 0, 0, 3, 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