Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1159d1e6a875becdea88b7f5e560643f52e0677083d14edd24a65acc0a1fa7a

Tx prefix hash: a8b401a5b35baef274ca05d975b4a7519318315591f7709dd68664683cb2ccce
Tx public key: d440651ce825aa093ee9aa7a2c4c6543b56e661914689269d3db4077e4ecb20c
Timestamp: 1716843496 Timestamp [UCT]: 2024-05-27 20:58:16 Age [y:d:h:m:s]: 01:170:10:41:27
Block: 1031397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380412 RingCT/type: yes/0
Extra: 01d440651ce825aa093ee9aa7a2c4c6543b56e661914689269d3db4077e4ecb20c02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b955d78e40c52994b4594c25d1e00109c7c3028d60180e5b21f5faeda8841b30 0.600000000000 1499838 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": 1031407, "vin": [ { "gen": { "height": 1031397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b955d78e40c52994b4594c25d1e00109c7c3028d60180e5b21f5faeda8841b30" } } ], "extra": [ 1, 212, 64, 101, 28, 232, 37, 170, 9, 62, 233, 170, 122, 44, 76, 101, 67, 181, 110, 102, 25, 20, 104, 146, 105, 211, 219, 64, 119, 228, 236, 178, 12, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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