Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61fb4b3ee936a7ee692ceccc55927a3a6f30a7a09d639502a15cd97d2decb8b3

Tx prefix hash: 4e45087f133edfd264c6b29794057222b4555455cfe0f63afb3b2c09eaee1752
Tx public key: f719d83c3e3f10bf72b278db72faf5628d752d5a542d59f2805317c3310c4c68
Timestamp: 1736892372 Timestamp [UCT]: 2025-01-14 22:06:12 Age [y:d:h:m:s]: 00:340:09:45:19
Block: 1197455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240855 RingCT/type: yes/0
Extra: 01f719d83c3e3f10bf72b278db72faf5628d752d5a542d59f2805317c3310c4c68021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c962cad7b30041b449146a58ff73d8b6c05a23f893816e5d4c124acbdd6d47ca 0.600000000000 1684062 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": 1197465, "vin": [ { "gen": { "height": 1197455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c962cad7b30041b449146a58ff73d8b6c05a23f893816e5d4c124acbdd6d47ca" } } ], "extra": [ 1, 247, 25, 216, 60, 62, 63, 16, 191, 114, 178, 120, 219, 114, 250, 245, 98, 141, 117, 45, 90, 84, 45, 89, 242, 128, 83, 23, 195, 49, 12, 76, 104, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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