Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0019778d6253f8cf26816c84091fb2e0c4033923df65b6dbde589811648213f2

Tx prefix hash: 0f37dd41123b1c2bb1dc0862e247b48daf5bb300f0576adb4fcc0ac69ad0d767
Tx public key: 1916dfb0db9dbee7d3ef2020d90fe9e74c16fa5410a858b01f08ab03a954227e
Timestamp: 1686063815 Timestamp [UCT]: 2023-06-06 15:03:35 Age [y:d:h:m:s]: 01:227:15:04:32
Block: 776457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424059 RingCT/type: yes/0
Extra: 011916dfb0db9dbee7d3ef2020d90fe9e74c16fa5410a858b01f08ab03a954227e02110000000675e3f0e9000000000000000000

1 output(s) for total of 1.641631968000 dcy

stealth address amount amount idx
00: 25aa9cb0b8a60835d0e99f8967bf0c8f403455bff806e0af549787b7d98ec48c 1.641631968000 1226012 of 0

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": 776467, "vin": [ { "gen": { "height": 776457 } } ], "vout": [ { "amount": 1641631968, "target": { "key": "25aa9cb0b8a60835d0e99f8967bf0c8f403455bff806e0af549787b7d98ec48c" } } ], "extra": [ 1, 25, 22, 223, 176, 219, 157, 190, 231, 211, 239, 32, 32, 217, 15, 233, 231, 76, 22, 250, 84, 16, 168, 88, 176, 31, 8, 171, 3, 169, 84, 34, 126, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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