Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f30084e99e32a81d506d7e931bea29ff9734d047e27e3c7a99478f9e0ce7f3d7

Tx prefix hash: 021f6d1893815188fe470b0ea88a0550263070f447defa912c8d214f9bbee61e
Tx public key: 8673cfbbd5f6259e531e9b6d807a3477b2267853a741f2b009ca8e2d1e446b7d
Timestamp: 1696681551 Timestamp [UCT]: 2023-10-07 12:25:51 Age [y:d:h:m:s]: 01:219:00:08:10
Block: 864436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417584 RingCT/type: yes/0
Extra: 018673cfbbd5f6259e531e9b6d807a3477b2267853a741f2b009ca8e2d1e446b7d021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.839005336000 dcy

stealth address amount amount idx
00: c49b0f4a56ec57b844370f0a6b92c9c7fe12489f07e9a2e9802fc06e451e80ee 0.839005336000 1318950 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": 864446, "vin": [ { "gen": { "height": 864436 } } ], "vout": [ { "amount": 839005336, "target": { "key": "c49b0f4a56ec57b844370f0a6b92c9c7fe12489f07e9a2e9802fc06e451e80ee" } } ], "extra": [ 1, 134, 115, 207, 187, 213, 246, 37, 158, 83, 30, 155, 109, 128, 122, 52, 119, 178, 38, 120, 83, 167, 65, 242, 176, 9, 202, 142, 45, 30, 68, 107, 125, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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