Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc7d6bc95751bb046905c3059c9e58596ffac799ad81408a5be51c2dcc4fb925

Tx prefix hash: b5b0dcf0e52d6703e9cb0faae92b2036a264f03839929c756f7b99bf0866d50b
Tx public key: 27918a1a149e91f8169f088a700a872cb64035e4eeb455520640b627781051b5
Timestamp: 1732993681 Timestamp [UCT]: 2024-11-30 19:08:01 Age [y:d:h:m:s]: 00:111:13:29:34
Block: 1165185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79528 RingCT/type: yes/0
Extra: 0127918a1a149e91f8169f088a700a872cb64035e4eeb455520640b627781051b5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b43fe27fbce77b2bb2b02e939789fb165cad4b8018c03af3d0d6a95d1fccbc5b 0.600000000000 1650860 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": 1165195, "vin": [ { "gen": { "height": 1165185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b43fe27fbce77b2bb2b02e939789fb165cad4b8018c03af3d0d6a95d1fccbc5b" } } ], "extra": [ 1, 39, 145, 138, 26, 20, 158, 145, 248, 22, 159, 8, 138, 112, 10, 135, 44, 182, 64, 53, 228, 238, 180, 85, 82, 6, 64, 182, 39, 120, 16, 81, 181, 2, 17, 0, 0, 0, 3, 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