Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0fda2e32f56950f8db47f8d5d2c5ee7895b2254fb76c8be17f080540010f5f9

Tx prefix hash: 8c9a4979017d1633a73c470cf6ece59891f9f37e1807453f2c5276c129404a11
Tx public key: f0c6d488618da590dc10d40b47b60c414be9b01630f079619df880fe371b178d
Timestamp: 1681446624 Timestamp [UCT]: 2023-04-14 04:30:24 Age [y:d:h:m:s]: 01:174:13:59:41
Block: 738164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386277 RingCT/type: yes/0
Extra: 01f0c6d488618da590dc10d40b47b60c414be9b01630f079619df880fe371b178d021100000002b3164c24000000000000000000

1 output(s) for total of 2.198651832000 dcy

stealth address amount amount idx
00: 5b54572a09460c42766eff7c341bd5b66b208d1d0c02322cf0a3c90a990c8f20 2.198651832000 1184817 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": 738174, "vin": [ { "gen": { "height": 738164 } } ], "vout": [ { "amount": 2198651832, "target": { "key": "5b54572a09460c42766eff7c341bd5b66b208d1d0c02322cf0a3c90a990c8f20" } } ], "extra": [ 1, 240, 198, 212, 136, 97, 141, 165, 144, 220, 16, 212, 11, 71, 182, 12, 65, 75, 233, 176, 22, 48, 240, 121, 97, 157, 248, 128, 254, 55, 27, 23, 141, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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