Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e4e3a020a6bfa35010bfaf6019eddbad4ffdf5bd0041f5aaaa6c03724e1e39

Tx prefix hash: 81f2fb388dab44b552d782b2b9cbdafc752d51a3e149b0f7dcc9e136dbf82580
Tx public key: 746f0428adeedbe52b1e4e3b64be959015a8d4b298a7c59881f2bba88534f2f0
Timestamp: 1726040603 Timestamp [UCT]: 2024-09-11 07:43:23 Age [y:d:h:m:s]: 00:208:16:33:55
Block: 1107634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148972 RingCT/type: yes/0
Extra: 01746f0428adeedbe52b1e4e3b64be959015a8d4b298a7c59881f2bba88534f2f002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ec57cbf007cf56f68b196b9df10eab6df8c3430c1ecb5e887f84831087605c2 0.600000000000 1585247 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": 1107644, "vin": [ { "gen": { "height": 1107634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ec57cbf007cf56f68b196b9df10eab6df8c3430c1ecb5e887f84831087605c2" } } ], "extra": [ 1, 116, 111, 4, 40, 173, 238, 219, 229, 43, 30, 78, 59, 100, 190, 149, 144, 21, 168, 212, 178, 152, 167, 197, 152, 129, 242, 187, 168, 133, 52, 242, 240, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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