Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6515ff5ff659c1fbc85eedb9c6f43766f053a65afdecbe9c5de5a398018ae72

Tx prefix hash: c230f81375d3041e9d5de7492e1e88b059ef9b876532abd91c6a8f6bcb080db5
Tx public key: 2511f2d7b59a65fa16d53a0cf878b5d7a7edf29eb063efdbfa60d5c5920525d1
Timestamp: 1709017469 Timestamp [UCT]: 2024-02-27 07:04:29 Age [y:d:h:m:s]: 01:111:12:48:08
Block: 966513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340649 RingCT/type: yes/0
Extra: 012511f2d7b59a65fa16d53a0cf878b5d7a7edf29eb063efdbfa60d5c5920525d1021100000006679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e27ca9b6763ba230c4bffad0187535d7c840527c351e4dda11d6be292fcd30c4 0.600000000000 1426272 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": 966523, "vin": [ { "gen": { "height": 966513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e27ca9b6763ba230c4bffad0187535d7c840527c351e4dda11d6be292fcd30c4" } } ], "extra": [ 1, 37, 17, 242, 215, 181, 154, 101, 250, 22, 213, 58, 12, 248, 120, 181, 215, 167, 237, 242, 158, 176, 99, 239, 219, 250, 96, 213, 197, 146, 5, 37, 209, 2, 17, 0, 0, 0, 6, 103, 154, 138, 129, 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