Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd90b235dac420d6d302f6f67b152ad87824f4c31b761edc6e4f8607305b48d0

Tx prefix hash: b70fca379a6d4a2e255a718ceb73bb687c0ef28140160865504d8e935498057b
Tx public key: de588d0b7dc5f50360ae937e303b6427012c047e0ac0c33c52c889780c4f3c89
Timestamp: 1734494861 Timestamp [UCT]: 2024-12-18 04:07:41 Age [y:d:h:m:s]: 00:338:07:54:31
Block: 1177645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239289 RingCT/type: yes/0
Extra: 01de588d0b7dc5f50360ae937e303b6427012c047e0ac0c33c52c889780c4f3c8902110000000139ec141b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77a4de256fd96d6e1210c40f9465b756404900537473c0eec383f8c400e1bda9 0.600000000000 1664018 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": 1177655, "vin": [ { "gen": { "height": 1177645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77a4de256fd96d6e1210c40f9465b756404900537473c0eec383f8c400e1bda9" } } ], "extra": [ 1, 222, 88, 141, 11, 125, 197, 245, 3, 96, 174, 147, 126, 48, 59, 100, 39, 1, 44, 4, 126, 10, 192, 195, 60, 82, 200, 137, 120, 12, 79, 60, 137, 2, 17, 0, 0, 0, 1, 57, 236, 20, 27, 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