Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ed155dd43ab79d57375bd1a4e85fcf31531fd601fede43f5e0928626647b416

Tx prefix hash: aa858b8911a7b196a4b1d9b2a02fe439d1bdb2f5ae70ffaaa35d14f946863993
Tx public key: 521d54ed985de176b36f1e000105f8e8e431e6e51a76d77407d4fcb96896700d
Timestamp: 1719324216 Timestamp [UCT]: 2024-06-25 14:03:36 Age [y:d:h:m:s]: 00:266:21:28:06
Block: 1051948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190724 RingCT/type: yes/0
Extra: 01521d54ed985de176b36f1e000105f8e8e431e6e51a76d77407d4fcb96896700d021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b0d5440cf3ad765bc49dad8b18f6bfd7c136a0ddc99d73ae4c7d041fba176d5 0.600000000000 1522269 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": 1051958, "vin": [ { "gen": { "height": 1051948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b0d5440cf3ad765bc49dad8b18f6bfd7c136a0ddc99d73ae4c7d041fba176d5" } } ], "extra": [ 1, 82, 29, 84, 237, 152, 93, 225, 118, 179, 111, 30, 0, 1, 5, 248, 232, 228, 49, 230, 229, 26, 118, 215, 116, 7, 212, 252, 185, 104, 150, 112, 13, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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