Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f914127df33b6c5757c6cb5ba86ca2a3690938223d8f9214a11ea54944eddb0e

Tx prefix hash: 713d88e78b7eb3261c82d1a43299f41ac4a8ed7e4b5348ed11e5686443badad2
Tx public key: f0c9dff3d4336931d162c015bb605677d16ab430e74e34108cdf0abb66d11e7e
Timestamp: 1729542952 Timestamp [UCT]: 2024-10-21 20:35:52 Age [y:d:h:m:s]: 00:092:22:53:09
Block: 1136626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66429 RingCT/type: yes/0
Extra: 01f0c9dff3d4336931d162c015bb605677d16ab430e74e34108cdf0abb66d11e7e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b9811fcd6be6d54bfe274d410904354ab3c2418f11b21bbabe4c388785d6c8d 0.600000000000 1619973 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": 1136636, "vin": [ { "gen": { "height": 1136626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b9811fcd6be6d54bfe274d410904354ab3c2418f11b21bbabe4c388785d6c8d" } } ], "extra": [ 1, 240, 201, 223, 243, 212, 51, 105, 49, 209, 98, 192, 21, 187, 96, 86, 119, 209, 106, 180, 48, 231, 78, 52, 16, 140, 223, 10, 187, 102, 209, 30, 126, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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