Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dabc58c5ff7da23876d50c79cbd2ecc8939985aa242f236108b7a1888bc01bd5

Tx prefix hash: 2c71bf313acb7561d1b8e92a3aa3f13468cbb87481c0fcbf8b483aa89c044057
Tx public key: cde3b27b0db4fde211cb31f0a5e13a84a6efe1cf4f5d3883479da6f650bf15a9
Timestamp: 1727573438 Timestamp [UCT]: 2024-09-29 01:30:38 Age [y:d:h:m:s]: 00:215:23:02:11
Block: 1120346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154163 RingCT/type: yes/0
Extra: 01cde3b27b0db4fde211cb31f0a5e13a84a6efe1cf4f5d3883479da6f650bf15a902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd734a27dd42c64912a9c5706e8e0ed25d6f3477c2e7bb8700f28bf3f590d822 0.600000000000 1602227 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": 1120356, "vin": [ { "gen": { "height": 1120346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd734a27dd42c64912a9c5706e8e0ed25d6f3477c2e7bb8700f28bf3f590d822" } } ], "extra": [ 1, 205, 227, 178, 123, 13, 180, 253, 226, 17, 203, 49, 240, 165, 225, 58, 132, 166, 239, 225, 207, 79, 93, 56, 131, 71, 157, 166, 246, 80, 191, 21, 169, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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