Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1799b16309c24f1a1c0af17aa6baeb3e2962a5ab78e41503a668b8ba3d050b5c

Tx prefix hash: 12813b516d2156c26c98a28f39f8544d2081b42ca56f93787e2f477bd6dec7a2
Tx public key: f1cd18a5d2173cb5ab5e7afcb711ec57fe6ca093c0540086aef305975a87d418
Timestamp: 1737692626 Timestamp [UCT]: 2025-01-24 04:23:46 Age [y:d:h:m:s]: 00:327:13:51:09
Block: 1204043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231694 RingCT/type: yes/0
Extra: 01f1cd18a5d2173cb5ab5e7afcb711ec57fe6ca093c0540086aef305975a87d4180211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a843d7eb505a7d10948753603ab56bebe0a85d310c85eef61ed37bc6a55e6b4f 0.600000000000 1690724 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": 1204053, "vin": [ { "gen": { "height": 1204043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a843d7eb505a7d10948753603ab56bebe0a85d310c85eef61ed37bc6a55e6b4f" } } ], "extra": [ 1, 241, 205, 24, 165, 210, 23, 60, 181, 171, 94, 122, 252, 183, 17, 236, 87, 254, 108, 160, 147, 192, 84, 0, 134, 174, 243, 5, 151, 90, 135, 212, 24, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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