Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d0779bfd1502aff5e49db987fbd7bd45f607372969c9e36d40583caef5061e6

Tx prefix hash: 49189b2914ccadd94dc00045cb4a953844d2ef00ae41fc72575a9b92ebaf57a7
Tx public key: 3edfaa223c7c8fd78326b7ab93d3fd36359a954fd46fbde44f81e11e3f9f20d5
Timestamp: 1702388538 Timestamp [UCT]: 2023-12-12 13:42:18 Age [y:d:h:m:s]: 01:147:11:00:12
Block: 911567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366528 RingCT/type: yes/0
Extra: 013edfaa223c7c8fd78326b7ab93d3fd36359a954fd46fbde44f81e11e3f9f20d5021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3f66ff3ad71c4d659dfe45efdb1ef375f08e90fdb781766516c9ee66de41c95 0.600000000000 1368779 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": 911577, "vin": [ { "gen": { "height": 911567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f66ff3ad71c4d659dfe45efdb1ef375f08e90fdb781766516c9ee66de41c95" } } ], "extra": [ 1, 62, 223, 170, 34, 60, 124, 143, 215, 131, 38, 183, 171, 147, 211, 253, 54, 53, 154, 149, 79, 212, 111, 189, 228, 79, 129, 225, 30, 63, 159, 32, 213, 2, 17, 0, 0, 0, 3, 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