Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91e830524514ff3c5622ea0ef767928f3f3fc6360a2a1fa6959db9e1d349de2c

Tx prefix hash: b929d23aac2563d5cc9623aff6e06808aa1858ea9480b9afd3fbdc5f53ad4bd0
Tx public key: e9da70920edffbda1052e34f5beb0f4ea059dba38d2bab52a18254a3d36ec369
Timestamp: 1738031995 Timestamp [UCT]: 2025-01-28 02:39:55 Age [y:d:h:m:s]: 00:139:11:35:55
Block: 1206646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99639 RingCT/type: yes/0
Extra: 01e9da70920edffbda1052e34f5beb0f4ea059dba38d2bab52a18254a3d36ec3690211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 455f5443c9a4441c7a551c0e28a4e04a4559c37e6ff6d4dd8567f72ede98a557 0.600000000000 1693357 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": 1206656, "vin": [ { "gen": { "height": 1206646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "455f5443c9a4441c7a551c0e28a4e04a4559c37e6ff6d4dd8567f72ede98a557" } } ], "extra": [ 1, 233, 218, 112, 146, 14, 223, 251, 218, 16, 82, 227, 79, 91, 235, 15, 78, 160, 89, 219, 163, 141, 43, 171, 82, 161, 130, 84, 163, 211, 110, 195, 105, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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