Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 830cace367663a7733a6de0d82883f1f7eda34f81dff9a28547c27bb7c02f0da

Tx prefix hash: 29fbd80c3b697dd62c4158556a0b1581e16d42defec3af1523fecd34ad90bdc8
Tx public key: be811426f4de933cc5976f1aa68db87acdf339b2e611ea8e1103364e66934a21
Timestamp: 1733805290 Timestamp [UCT]: 2024-12-10 04:34:50 Age [y:d:h:m:s]: 00:142:10:29:10
Block: 1171911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101595 RingCT/type: yes/0
Extra: 01be811426f4de933cc5976f1aa68db87acdf339b2e611ea8e1103364e66934a21021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2306e1075ba3e0f6640aeae5c8d30a641ceb2c20bd5b98e703a30c7ea3ccb9a6 0.600000000000 1657734 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": 1171921, "vin": [ { "gen": { "height": 1171911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2306e1075ba3e0f6640aeae5c8d30a641ceb2c20bd5b98e703a30c7ea3ccb9a6" } } ], "extra": [ 1, 190, 129, 20, 38, 244, 222, 147, 60, 197, 151, 111, 26, 166, 141, 184, 122, 205, 243, 57, 178, 230, 17, 234, 142, 17, 3, 54, 78, 102, 147, 74, 33, 2, 17, 0, 0, 0, 1, 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