Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08094d897ed85e5b125a17e2e6fb8aa05df6bc63fb836430eea5ed5490a54418

Tx prefix hash: 8e0a8826dec31bf8e2f94a9d4e21b0bcc4df01293e145fa0433e47ef61e62303
Tx public key: a79ed2113a9631b30e67bf97765bd158dd9a04208a45cfa64c490ef3b2389fbc
Timestamp: 1704319808 Timestamp [UCT]: 2024-01-03 22:10:08 Age [y:d:h:m:s]: 01:333:12:44:29
Block: 927572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497220 RingCT/type: yes/0
Extra: 01a79ed2113a9631b30e67bf97765bd158dd9a04208a45cfa64c490ef3b2389fbc021100000007e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bd376adb5bd22ca915c3d15ceb7998215d7cb378de0b5b3bdc9caaa7ac7525c 0.600000000000 1385408 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": 927582, "vin": [ { "gen": { "height": 927572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bd376adb5bd22ca915c3d15ceb7998215d7cb378de0b5b3bdc9caaa7ac7525c" } } ], "extra": [ 1, 167, 158, 210, 17, 58, 150, 49, 179, 14, 103, 191, 151, 118, 91, 209, 88, 221, 154, 4, 32, 138, 69, 207, 166, 76, 73, 14, 243, 178, 56, 159, 188, 2, 17, 0, 0, 0, 7, 224, 133, 50, 182, 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