Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba03d9bca5be0b983098d1ab3264e2b88336ebe93539040b36040ba9c2bb914f

Tx prefix hash: 548930add4ebc9af6254c3d5e927cc34d79284f18d3b12d07e5342feb7fb883b
Tx public key: 4d5f3c6ad2ba8a41b5b279a1356007813925bc64073a55eb36823ae82881699e
Timestamp: 1702347034 Timestamp [UCT]: 2023-12-12 02:10:34 Age [y:d:h:m:s]: 01:333:16:45:19
Block: 911207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497348 RingCT/type: yes/0
Extra: 014d5f3c6ad2ba8a41b5b279a1356007813925bc64073a55eb36823ae82881699e021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c27b322b8f813e5aa38a595559795e430685290e122c8e01504b0d29889a089 0.600000000000 1368388 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": 911217, "vin": [ { "gen": { "height": 911207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c27b322b8f813e5aa38a595559795e430685290e122c8e01504b0d29889a089" } } ], "extra": [ 1, 77, 95, 60, 106, 210, 186, 138, 65, 181, 178, 121, 161, 53, 96, 7, 129, 57, 37, 188, 100, 7, 58, 85, 235, 54, 130, 58, 232, 40, 129, 105, 158, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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