Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3394720227b1b147b1229ae2a84f82ca80c1ddb0b40424935172b1ecfaafc407

Tx prefix hash: 191a31c27fad4475b059910caff40412918ca583ead8bc0de985bb5f7be717b4
Tx public key: 3c1ad293e35d1e54ea886bd3fba9aad5c0554704f6eca2d9295cb444f0d6f1f5
Timestamp: 1682008183 Timestamp [UCT]: 2023-04-20 16:29:43 Age [y:d:h:m:s]: 01:311:23:03:29
Block: 742834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484192 RingCT/type: yes/0
Extra: 013c1ad293e35d1e54ea886bd3fba9aad5c0554704f6eca2d9295cb444f0d6f1f5021100000002e7ace25d000000000000000000

1 output(s) for total of 2.121694285000 dcy

stealth address amount amount idx
00: 4138fe64de9cd7443d03b48f3786a21a0fa36e90d7fa4ea31fa7dd420397db30 2.121694285000 1189837 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": 742844, "vin": [ { "gen": { "height": 742834 } } ], "vout": [ { "amount": 2121694285, "target": { "key": "4138fe64de9cd7443d03b48f3786a21a0fa36e90d7fa4ea31fa7dd420397db30" } } ], "extra": [ 1, 60, 26, 210, 147, 227, 93, 30, 84, 234, 136, 107, 211, 251, 169, 170, 213, 192, 85, 71, 4, 246, 236, 162, 217, 41, 92, 180, 68, 240, 214, 241, 245, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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