Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d72fa960355087b0a64c8cfbc31d72829d16462c270f78261cb5586ee54b0dc4

Tx prefix hash: d359c6d3ce084bef06a12c1f87b9f95c4b97e89c3a56fda647ac8f6949d89d70
Tx public key: 89cf1244037115e0ac157c5f1895ae5a985f6ccb516dd9e559fa703a306c75fe
Timestamp: 1705469571 Timestamp [UCT]: 2024-01-17 05:32:51 Age [y:d:h:m:s]: 01:299:07:56:55
Block: 937059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472767 RingCT/type: yes/0
Extra: 0189cf1244037115e0ac157c5f1895ae5a985f6ccb516dd9e559fa703a306c75fe02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 362115ab4e7f18bade4d0fc12e50894f4788b2bc3b0da74b5f3ad6cf401a5c07 0.600000000000 1395103 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": 937069, "vin": [ { "gen": { "height": 937059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "362115ab4e7f18bade4d0fc12e50894f4788b2bc3b0da74b5f3ad6cf401a5c07" } } ], "extra": [ 1, 137, 207, 18, 68, 3, 113, 21, 224, 172, 21, 124, 95, 24, 149, 174, 90, 152, 95, 108, 203, 81, 109, 217, 229, 89, 250, 112, 58, 48, 108, 117, 254, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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