Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792bea703842a1488ad287f629ee2f3b4176f99dcc7e37962a8fce5822668e75

Tx prefix hash: f98b3f4887bfe336ccf75b4957acd69d54bb22a5697e0c170375549edb113e09
Tx public key: a763a6f5e2287ace3e1f4c01f91d68a2872fc0574eddbcb34ea6f1ec29b2bc5a
Timestamp: 1747486468 Timestamp [UCT]: 2025-05-17 12:54:28 Age [y:d:h:m:s]: 00:235:23:49:17
Block: 1284895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166444 RingCT/type: yes/0
Extra: 01a763a6f5e2287ace3e1f4c01f91d68a2872fc0574eddbcb34ea6f1ec29b2bc5a0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28b1882459d8e0feb75abb1dce09209a117672d8ebdc89ee8a47a84be9e1c199 0.600000000000 1772358 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": 1284905, "vin": [ { "gen": { "height": 1284895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b1882459d8e0feb75abb1dce09209a117672d8ebdc89ee8a47a84be9e1c199" } } ], "extra": [ 1, 167, 99, 166, 245, 226, 40, 122, 206, 62, 31, 76, 1, 249, 29, 104, 162, 135, 47, 192, 87, 78, 221, 188, 179, 78, 166, 241, 236, 41, 178, 188, 90, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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