Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657663622d3451c61c1c1db892db486987c4dfd342ce96bc13d85dc738910325

Tx prefix hash: cc3ae5781ea571fda6a351235e8fd3cbb1699a0fd38c8a5d8531d4190528af08
Tx public key: 165d97f6238ff8b2543f262a4942fad12885b42b5ac5d22550624e646e0c8f7c
Timestamp: 1715862644 Timestamp [UCT]: 2024-05-16 12:30:44 Age [y:d:h:m:s]: 00:326:01:27:27
Block: 1023258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233058 RingCT/type: yes/0
Extra: 01165d97f6238ff8b2543f262a4942fad12885b42b5ac5d22550624e646e0c8f7c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad923d9427f9718603a16fe9c42ce8ed01b873b3ca15abe816e4d2e1f5657bb 0.600000000000 1488111 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": 1023268, "vin": [ { "gen": { "height": 1023258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad923d9427f9718603a16fe9c42ce8ed01b873b3ca15abe816e4d2e1f5657bb" } } ], "extra": [ 1, 22, 93, 151, 246, 35, 143, 248, 178, 84, 63, 38, 42, 73, 66, 250, 209, 40, 133, 180, 43, 90, 197, 210, 37, 80, 98, 78, 100, 110, 12, 143, 124, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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