Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e621031adb9f84b17a522b64780dddbbe636cc64212ea11b493170347442a4e

Tx prefix hash: fcd00df35376cb5dfefd1c555dc876fa128894055f48d0a4a6e78a8a5aaab74f
Tx public key: a4ec085143c4771eb64c3074e083aa79f30c2d16ca5af1fdcf175e83421e2f58
Timestamp: 1717595569 Timestamp [UCT]: 2024-06-05 13:52:49 Age [y:d:h:m:s]: 00:358:15:37:37
Block: 1037619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256360 RingCT/type: yes/0
Extra: 01a4ec085143c4771eb64c3074e083aa79f30c2d16ca5af1fdcf175e83421e2f5802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34a6e1bc45c5e6bc12c802bc9e2f74961e3d04e93435a979b004d3d5c378431f 0.600000000000 1506172 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": 1037629, "vin": [ { "gen": { "height": 1037619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34a6e1bc45c5e6bc12c802bc9e2f74961e3d04e93435a979b004d3d5c378431f" } } ], "extra": [ 1, 164, 236, 8, 81, 67, 196, 119, 30, 182, 76, 48, 116, 224, 131, 170, 121, 243, 12, 45, 22, 202, 90, 241, 253, 207, 23, 94, 131, 66, 30, 47, 88, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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