Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d384f1f4cf9c85e566442335900df3d20f62c0f16dd54621bbb6d5f679d6a188

Tx prefix hash: 97a78448b7cece01716ee4b4bc72764df7f242e7f463f4c2b6859bc950baf73c
Tx public key: fa69c4a30c1c55e70dcf6dd57d3b7a5b2c73dc9bda92ea0a0385d41927269897
Timestamp: 1672878612 Timestamp [UCT]: 2023-01-05 00:30:12 Age [y:d:h:m:s]: 02:097:01:13:56
Block: 667750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591061 RingCT/type: yes/0
Extra: 01fa69c4a30c1c55e70dcf6dd57d3b7a5b2c73dc9bda92ea0a0385d41927269897021100000006e6d27f9c000000000000000000

1 output(s) for total of 3.762417747000 dcy

stealth address amount amount idx
00: d4f2287a256aaa45f58dfd20d6de48ace5a5dc9d696164937731c0952ceac13c 3.762417747000 1108967 of 0

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": 667760, "vin": [ { "gen": { "height": 667750 } } ], "vout": [ { "amount": 3762417747, "target": { "key": "d4f2287a256aaa45f58dfd20d6de48ace5a5dc9d696164937731c0952ceac13c" } } ], "extra": [ 1, 250, 105, 196, 163, 12, 28, 85, 231, 13, 207, 109, 213, 125, 59, 122, 91, 44, 115, 220, 155, 218, 146, 234, 10, 3, 133, 212, 25, 39, 38, 152, 151, 2, 17, 0, 0, 0, 6, 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