Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58ac1e126db62e10084bc7d21c1c0e3bc195e1cde9caa1d8ea24e7cb6a921356

Tx prefix hash: 3b8d6512e1b64815f8f59f2f279034bbae23f893269d3940b913d8fbef1d9fa4
Tx public key: 0b23a0f83c59299a370d6713fde2a20b4861ca5b4ee408daa7fc3cfa1bc91b2a
Timestamp: 1733633348 Timestamp [UCT]: 2024-12-08 04:49:08 Age [y:d:h:m:s]: 00:113:07:35:09
Block: 1170480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80784 RingCT/type: yes/0
Extra: 010b23a0f83c59299a370d6713fde2a20b4861ca5b4ee408daa7fc3cfa1bc91b2a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9f3f3b2808753bb37cc3c55295d2b05d62075749d7c225dd68c9fc1d8b4db3 0.600000000000 1656211 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": 1170490, "vin": [ { "gen": { "height": 1170480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9f3f3b2808753bb37cc3c55295d2b05d62075749d7c225dd68c9fc1d8b4db3" } } ], "extra": [ 1, 11, 35, 160, 248, 60, 89, 41, 154, 55, 13, 103, 19, 253, 226, 162, 11, 72, 97, 202, 91, 78, 228, 8, 218, 167, 252, 60, 250, 27, 201, 27, 42, 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