Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 654f1bf1ed3df0f83a0f7f7aeaa00f1062959ace1c46f641c5615e4914cb0a00

Tx prefix hash: 65af723ac964bd7765080428637c8bc1bb22f4e852a3822c949e6fb30230d74d
Tx public key: eb4b5ec7059b8d105eda40ae4f5753fdf7c45d29349508fa3327b538c2582903
Timestamp: 1706413119 Timestamp [UCT]: 2024-01-28 03:38:39 Age [y:d:h:m:s]: 01:140:17:23:54
Block: 944891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361599 RingCT/type: yes/0
Extra: 01eb4b5ec7059b8d105eda40ae4f5753fdf7c45d29349508fa3327b538c258290302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 625f261bf0975270cb951859414b2bb44d31869049d1a9a97a6522cd4728d1c8 0.600000000000 1403185 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": 944901, "vin": [ { "gen": { "height": 944891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "625f261bf0975270cb951859414b2bb44d31869049d1a9a97a6522cd4728d1c8" } } ], "extra": [ 1, 235, 75, 94, 199, 5, 155, 141, 16, 94, 218, 64, 174, 79, 87, 83, 253, 247, 196, 93, 41, 52, 149, 8, 250, 51, 39, 181, 56, 194, 88, 41, 3, 2, 17, 0, 0, 0, 6, 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