Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 129380ed8ed53dff6307039d775fbfc0c53e0f98df9e1b7a1ba2936da3bb078a

Tx prefix hash: 1265f25428791303369467509c7ae4f93afdddd260f753d9b7f336f6ab608b40
Tx public key: c9e4c08189c9353c7fbcfee49c95d6f6037b305ab8bcb47fe67c7350f53649ce
Timestamp: 1727940514 Timestamp [UCT]: 2024-10-03 07:28:34 Age [y:d:h:m:s]: 00:115:02:00:30
Block: 1123383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82240 RingCT/type: yes/0
Extra: 01c9e4c08189c9353c7fbcfee49c95d6f6037b305ab8bcb47fe67c7350f53649ce021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a1e3ef5d47b43167440e12f65d56feb04559cb684a3c4d2c95b8a4b95385062 0.600000000000 1605916 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": 1123393, "vin": [ { "gen": { "height": 1123383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a1e3ef5d47b43167440e12f65d56feb04559cb684a3c4d2c95b8a4b95385062" } } ], "extra": [ 1, 201, 228, 192, 129, 137, 201, 53, 60, 127, 188, 254, 228, 156, 149, 214, 246, 3, 123, 48, 90, 184, 188, 180, 127, 230, 124, 115, 80, 245, 54, 73, 206, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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