Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44006bd3523a027b4cd30df94f002d5d2a72bc1ff6ffec9ad6b34a06553ef097

Tx prefix hash: 08559ecfb250d698a33741089b487f35e6b2e794851cb5bc15feeaf55cf840bd
Tx public key: d4b2f5f3ed2127cc613781b1e902b5f36a831028ea7fd0e011f220714736865e
Timestamp: 1730383994 Timestamp [UCT]: 2024-10-31 14:13:14 Age [y:d:h:m:s]: 00:082:19:27:50
Block: 1143567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59202 RingCT/type: yes/0
Extra: 01d4b2f5f3ed2127cc613781b1e902b5f36a831028ea7fd0e011f220714736865e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 296670e9aad8c4349320d809f272c9f1d60afee13fc364f45d8e4c107551ff8b 0.600000000000 1627484 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": 1143577, "vin": [ { "gen": { "height": 1143567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "296670e9aad8c4349320d809f272c9f1d60afee13fc364f45d8e4c107551ff8b" } } ], "extra": [ 1, 212, 178, 245, 243, 237, 33, 39, 204, 97, 55, 129, 177, 233, 2, 181, 243, 106, 131, 16, 40, 234, 127, 208, 224, 17, 242, 32, 113, 71, 54, 134, 94, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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