Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d31bff4c66d53220e64b3ca79f491810832a9b3729e7fcf9b59c1bde70986242

Tx prefix hash: 46bf33ee3b6287b71d33e8368f64fd2c15ab06062e2500eb5d698aa19db26ab7
Tx public key: 9614f81c815c49ae0bc5dddba51f5debbd8f52bff6755f6b44a74396da3b2478
Timestamp: 1719257920 Timestamp [UCT]: 2024-06-24 19:38:40 Age [y:d:h:m:s]: 00:351:09:56:12
Block: 1051394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251152 RingCT/type: yes/0
Extra: 019614f81c815c49ae0bc5dddba51f5debbd8f52bff6755f6b44a74396da3b2478021100000005a6fba9af000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d58e63b030558b095743c64bbf2fd1e3c9a45265df15a1b70d3654a9154a9aa3 0.600000000000 1521705 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": 1051404, "vin": [ { "gen": { "height": 1051394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d58e63b030558b095743c64bbf2fd1e3c9a45265df15a1b70d3654a9154a9aa3" } } ], "extra": [ 1, 150, 20, 248, 28, 129, 92, 73, 174, 11, 197, 221, 219, 165, 31, 93, 235, 189, 143, 82, 191, 246, 117, 95, 107, 68, 167, 67, 150, 218, 59, 36, 120, 2, 17, 0, 0, 0, 5, 166, 251, 169, 175, 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