Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29364de02789d41ad161a689dd2ae5c129530a516052bb83fb5ec58b9833dd62

Tx prefix hash: 90f29249fa39b618b9ffaa43ec2b9d03618f6c6b4aa3e135dbcd853b0147f8aa
Tx public key: 18dfc2c7fe617e8bbc2264d55cee6fe5aeb3858211c01b7edb8accb2f2c792fe
Timestamp: 1710861423 Timestamp [UCT]: 2024-03-19 15:17:03 Age [y:d:h:m:s]: 01:044:07:07:43
Block: 981811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292640 RingCT/type: yes/0
Extra: 0118dfc2c7fe617e8bbc2264d55cee6fe5aeb3858211c01b7edb8accb2f2c792fe021100000004a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c1212bcbeb32e4013d48b4d5cddce731a0afaa8f7cc2294ea8f69285df484dc 0.600000000000 1441910 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": 981821, "vin": [ { "gen": { "height": 981811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c1212bcbeb32e4013d48b4d5cddce731a0afaa8f7cc2294ea8f69285df484dc" } } ], "extra": [ 1, 24, 223, 194, 199, 254, 97, 126, 139, 188, 34, 100, 213, 92, 238, 111, 229, 174, 179, 133, 130, 17, 192, 27, 126, 219, 138, 204, 178, 242, 199, 146, 254, 2, 17, 0, 0, 0, 4, 165, 223, 157, 134, 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