Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c0fe2af271a4ae0a15401d8dd972232b0b2e26a71e044d5a88d150de6e07931

Tx prefix hash: b94e7560d3ead9e1f9b7b82c1a60c93d9a66022f25e4058bc77f6dee66749ee9
Tx public key: cf585dd8cc34f96ad2aa0dad877ae5dd7c31b076f6638525a837e7ad6c795fa0
Timestamp: 1749553557 Timestamp [UCT]: 2025-06-10 11:05:57 Age [y:d:h:m:s]: 00:155:00:04:49
Block: 1302023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108450 RingCT/type: yes/0
Extra: 01cf585dd8cc34f96ad2aa0dad877ae5dd7c31b076f6638525a837e7ad6c795fa00211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc0290d162435ecb413902837e1d43ad086f93a3c384a23c909dde60d2d7658c 0.600000000000 1789592 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": 1302033, "vin": [ { "gen": { "height": 1302023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc0290d162435ecb413902837e1d43ad086f93a3c384a23c909dde60d2d7658c" } } ], "extra": [ 1, 207, 88, 93, 216, 204, 52, 249, 106, 210, 170, 13, 173, 135, 122, 229, 221, 124, 49, 176, 118, 246, 99, 133, 37, 168, 55, 231, 173, 108, 121, 95, 160, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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