Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24fb5cdd27bfbe29c9cda41ee36261176b26d7b597877b792a897b787779de01

Tx prefix hash: 4953a1681bf58e45d59bd9ccafc6dca13d9e7318707928970437ad1a9435331c
Tx public key: aea9882dcfaa4a1b8efc0543e041c4f2e7d25c33ee07871dd6f57b1cb1732bd4
Timestamp: 1674316403 Timestamp [UCT]: 2023-01-21 15:53:23 Age [y:d:h:m:s]: 02:075:12:40:00
Block: 679680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575642 RingCT/type: yes/0
Extra: 01aea9882dcfaa4a1b8efc0543e041c4f2e7d25c33ee07871dd6f57b1cb1732bd40211000000015029cbac000000000000000000

1 output(s) for total of 3.435088690000 dcy

stealth address amount amount idx
00: a2e634d4f33f5152889cfdf633749b794a3c7c745701e1799bbfb072617a93f3 3.435088690000 1121687 of 0

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": 679690, "vin": [ { "gen": { "height": 679680 } } ], "vout": [ { "amount": 3435088690, "target": { "key": "a2e634d4f33f5152889cfdf633749b794a3c7c745701e1799bbfb072617a93f3" } } ], "extra": [ 1, 174, 169, 136, 45, 207, 170, 74, 27, 142, 252, 5, 67, 224, 65, 196, 242, 231, 210, 92, 51, 238, 7, 135, 29, 214, 245, 123, 28, 177, 115, 43, 212, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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