Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db1758f44649ec8b79538d59d433a9d4094e5207448fa4f8682ed56cfc99603a

Tx prefix hash: 3d52946bea5ec9f8a335ab824672d8fb9f65c8d266c5a52f4cc68afe4848d594
Tx public key: aa54ef2554f5b8b6a34167dcbf5079fc7a15d84986f5ff96c52383b2d8613eef
Timestamp: 1725921410 Timestamp [UCT]: 2024-09-09 22:36:50 Age [y:d:h:m:s]: 01:059:05:01:02
Block: 1106646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300736 RingCT/type: yes/0
Extra: 01aa54ef2554f5b8b6a34167dcbf5079fc7a15d84986f5ff96c52383b2d8613eef021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 195fbcd51ed09add551a5d6d2e3c2ef5d38577ac8020bbed0c114a0d0dfa6cfc 0.600000000000 1584247 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": 1106656, "vin": [ { "gen": { "height": 1106646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "195fbcd51ed09add551a5d6d2e3c2ef5d38577ac8020bbed0c114a0d0dfa6cfc" } } ], "extra": [ 1, 170, 84, 239, 37, 84, 245, 184, 182, 163, 65, 103, 220, 191, 80, 121, 252, 122, 21, 216, 73, 134, 245, 255, 150, 197, 35, 131, 178, 216, 97, 62, 239, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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