Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 744f6478409d2e82ac2dbe3966f2cf8a407bd7b2b3b0433ddc0031391c43f013

Tx prefix hash: 8d028302a0e06c9db1ed46e808e6eac01939fc87f29cf78b9a1dc66402f13ef6
Tx public key: 0eacab51f2fcfeef8f2348361ec193ec2223b6dd0be4b0f3508bc4a6e8cf15af
Timestamp: 1714392421 Timestamp [UCT]: 2024-04-29 12:07:01 Age [y:d:h:m:s]: 01:190:18:21:42
Block: 1011061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394964 RingCT/type: yes/0
Extra: 010eacab51f2fcfeef8f2348361ec193ec2223b6dd0be4b0f3508bc4a6e8cf15af0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 957906603866d8124bdadda459df16cba2e82d408a546b6a0df433b41cbea687 0.600000000000 1473189 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": 1011071, "vin": [ { "gen": { "height": 1011061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "957906603866d8124bdadda459df16cba2e82d408a546b6a0df433b41cbea687" } } ], "extra": [ 1, 14, 172, 171, 81, 242, 252, 254, 239, 143, 35, 72, 54, 30, 193, 147, 236, 34, 35, 182, 221, 11, 228, 176, 243, 80, 139, 196, 166, 232, 207, 21, 175, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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