Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c77b395646b5080997b7da8592d4afa91034d56eb5c14d1745d885d53440cd47

Tx prefix hash: 92baf1cf7134305b0f6615e58986e5cf87cde43c8e72fabd2a0b253c02e0203c
Tx public key: 4feecdd949b9fda0d8cbc5321f95ee382d89a83e45ad463dcf8f54c8583d34fc
Timestamp: 1720919655 Timestamp [UCT]: 2024-07-14 01:14:15 Age [y:d:h:m:s]: 00:313:22:02:59
Block: 1065198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224306 RingCT/type: yes/0
Extra: 014feecdd949b9fda0d8cbc5321f95ee382d89a83e45ad463dcf8f54c8583d34fc021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5af934e4e2cf58efb86e075432b0f1d5852812b34ad21e61c713ea24d3a9ae89 0.600000000000 1535743 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": 1065208, "vin": [ { "gen": { "height": 1065198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5af934e4e2cf58efb86e075432b0f1d5852812b34ad21e61c713ea24d3a9ae89" } } ], "extra": [ 1, 79, 238, 205, 217, 73, 185, 253, 160, 216, 203, 197, 50, 31, 149, 238, 56, 45, 137, 168, 62, 69, 173, 70, 61, 207, 143, 84, 200, 88, 61, 52, 252, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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