Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2fd1094f2c600569e7ccce793a43432cc8e3f28473b494f696a6f95590d3cf5

Tx prefix hash: 670cd6c79d00c81c52be9da136148ec6f136bc7927e5c5bec253ad5c9fa396cd
Tx public key: e0a13c3251410a754c12aaaf5a803d78d1369870d81086ad7a25a42726d0b198
Timestamp: 1731670632 Timestamp [UCT]: 2024-11-15 11:37:12 Age [y:d:h:m:s]: 00:147:11:20:28
Block: 1154217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105231 RingCT/type: yes/0
Extra: 01e0a13c3251410a754c12aaaf5a803d78d1369870d81086ad7a25a42726d0b198021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d397ed85e9ff4db830951ef4f9e331601cd65ce1d8abf93ac440ac8d36c75a3 0.600000000000 1639828 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": 1154227, "vin": [ { "gen": { "height": 1154217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d397ed85e9ff4db830951ef4f9e331601cd65ce1d8abf93ac440ac8d36c75a3" } } ], "extra": [ 1, 224, 161, 60, 50, 81, 65, 10, 117, 76, 18, 170, 175, 90, 128, 61, 120, 209, 54, 152, 112, 216, 16, 134, 173, 122, 37, 164, 39, 38, 208, 177, 152, 2, 17, 0, 0, 0, 2, 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