Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0794e5f70e3fc4887d3c7a2e06b7a7d1f74d10d50558f5dfff4f00dc3797aa4b

Tx prefix hash: 694a2e9fedc9c45b6427683362d1f3d0b8c8602b62bcfc4ad5982fb239d5bdb3
Tx public key: 5bcee188209c5c73cb0430f0d8f21bf9dda851cd254217a0d09685a9bff829d7
Timestamp: 1704954798 Timestamp [UCT]: 2024-01-11 06:33:18 Age [y:d:h:m:s]: 01:122:05:50:29
Block: 932803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348500 RingCT/type: yes/0
Extra: 015bcee188209c5c73cb0430f0d8f21bf9dda851cd254217a0d09685a9bff829d702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d15e3d483d3ea230d5dba091bc794dd3e8880bd4de5f578ae9ff45d15f0ab9eb 0.600000000000 1390743 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": 932813, "vin": [ { "gen": { "height": 932803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d15e3d483d3ea230d5dba091bc794dd3e8880bd4de5f578ae9ff45d15f0ab9eb" } } ], "extra": [ 1, 91, 206, 225, 136, 32, 156, 92, 115, 203, 4, 48, 240, 216, 242, 27, 249, 221, 168, 81, 205, 37, 66, 23, 160, 208, 150, 133, 169, 191, 248, 41, 215, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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