Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1763f07f65f0069b2d7bbe8b83a247557f7043fb8dc9a7107f2f98a0ed3557

Tx prefix hash: a4997b8c761d61332d5078c6879519cfa3d8d8936e47c9c9e9111473e55ee02a
Tx public key: 595f882c51af410c2471d98f59e5d4e61265b031d531ce74e534a8c5e5faba1d
Timestamp: 1680003142 Timestamp [UCT]: 2023-03-28 11:32:22 Age [y:d:h:m:s]: 01:235:15:09:24
Block: 726861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429238 RingCT/type: yes/0
Extra: 01595f882c51af410c2471d98f59e5d4e61265b031d531ce74e534a8c5e5faba1d021100000001b3164c24000000000000000000

1 output(s) for total of 2.396668731000 dcy

stealth address amount amount idx
00: 3d9c800a09ec4834b2c13a100d2d334d301f03466e862b5b33f4fdd0af7d4a47 2.396668731000 1172128 of 0

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": 726871, "vin": [ { "gen": { "height": 726861 } } ], "vout": [ { "amount": 2396668731, "target": { "key": "3d9c800a09ec4834b2c13a100d2d334d301f03466e862b5b33f4fdd0af7d4a47" } } ], "extra": [ 1, 89, 95, 136, 44, 81, 175, 65, 12, 36, 113, 217, 143, 89, 229, 212, 230, 18, 101, 176, 49, 213, 49, 206, 116, 229, 52, 168, 197, 229, 250, 186, 29, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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