Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b354b3d4f3ac8d85e338c893f37fd34a6f539ba2d8a7c5b7404204f085492dc

Tx prefix hash: 175891a870fc3df1a59a132db2fd6b72f784258980a45d7d326a6f1f1fee14e4
Tx public key: 8687dcb7c2c33edca6c9db09fc59659ea1d8d3dc1752548e281889a97ac85d38
Timestamp: 1748917898 Timestamp [UCT]: 2025-06-03 02:31:38 Age [y:d:h:m:s]: 00:214:11:52:40
Block: 1296760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151054 RingCT/type: yes/0
Extra: 018687dcb7c2c33edca6c9db09fc59659ea1d8d3dc1752548e281889a97ac85d3802110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 693cce25aeb904b86c1df37c5e2e8f5a87fc934683348b72f7a8280b60156ad0 0.600000000000 1784275 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": 1296770, "vin": [ { "gen": { "height": 1296760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "693cce25aeb904b86c1df37c5e2e8f5a87fc934683348b72f7a8280b60156ad0" } } ], "extra": [ 1, 134, 135, 220, 183, 194, 195, 62, 220, 166, 201, 219, 9, 252, 89, 101, 158, 161, 216, 211, 220, 23, 82, 84, 142, 40, 24, 137, 169, 122, 200, 93, 56, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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