Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13eb50d6b85884fab19c37ae56908735be50d83549e3fcc3690211f0cee4e06e

Tx prefix hash: 33b9017a64cbe3dcf0a0131fc033b1bf02c139be4eb67d696d6bbfab8fe82afe
Tx public key: b0b0d2753dff1a724e36b839f895a9660fdb33a43c93c58f916694d4d6768255
Timestamp: 1729373410 Timestamp [UCT]: 2024-10-19 21:30:10 Age [y:d:h:m:s]: 00:145:15:02:42
Block: 1135269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103862 RingCT/type: yes/0
Extra: 01b0b0d2753dff1a724e36b839f895a9660fdb33a43c93c58f916694d4d6768255021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91e1c23bf501decf386163a9fbbeb94f707382a7f9d95e238f06bf7f744c501e 0.600000000000 1618600 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": 1135279, "vin": [ { "gen": { "height": 1135269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91e1c23bf501decf386163a9fbbeb94f707382a7f9d95e238f06bf7f744c501e" } } ], "extra": [ 1, 176, 176, 210, 117, 61, 255, 26, 114, 78, 54, 184, 57, 248, 149, 169, 102, 15, 219, 51, 164, 60, 147, 197, 143, 145, 102, 148, 212, 214, 118, 130, 85, 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