Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ecfc88f5474b2e847e11db7c069f64d0c9c053971dfc91302c2a15a650f6d12

Tx prefix hash: 3880d247b294be526e06689afe10fd9e6dada711aced9281706240437325b518
Tx public key: 4d7605f3f1a57a86eb4cc8e89bad850ce2fd82606b5e4cb3401ece9a187b1875
Timestamp: 1735297270 Timestamp [UCT]: 2024-12-27 11:01:10 Age [y:d:h:m:s]: 00:102:06:15:14
Block: 1184252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72872 RingCT/type: yes/0
Extra: 014d7605f3f1a57a86eb4cc8e89bad850ce2fd82606b5e4cb3401ece9a187b1875021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c470476d3bd6371a1360e2518b10c424ca759d87cbdc9151c331b09fe48d8837 0.600000000000 1670707 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": 1184262, "vin": [ { "gen": { "height": 1184252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c470476d3bd6371a1360e2518b10c424ca759d87cbdc9151c331b09fe48d8837" } } ], "extra": [ 1, 77, 118, 5, 243, 241, 165, 122, 134, 235, 76, 200, 232, 155, 173, 133, 12, 226, 253, 130, 96, 107, 94, 76, 179, 64, 30, 206, 154, 24, 123, 24, 117, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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