Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f147fa0352564277bb2f51e767d42db511f260c504035057e039a44ce8bf949e

Tx prefix hash: e7d44e52bf27e3226428e1b3f0e3d95ea67a8814f584f8d91449fd660e249b14
Tx public key: 84e3bb809016f2981d237e0ac469ec7c8f17d109a75be7aca429a4bf12db78f6
Timestamp: 1733744885 Timestamp [UCT]: 2024-12-09 11:48:05 Age [y:d:h:m:s]: 00:344:08:55:39
Block: 1171404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243647 RingCT/type: yes/0
Extra: 0184e3bb809016f2981d237e0ac469ec7c8f17d109a75be7aca429a4bf12db78f6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6876a9d872a17fc2f068e088d036807bd27fd88bc8eeb6c307c53085bd0b2b1a 0.600000000000 1657157 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": 1171414, "vin": [ { "gen": { "height": 1171404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6876a9d872a17fc2f068e088d036807bd27fd88bc8eeb6c307c53085bd0b2b1a" } } ], "extra": [ 1, 132, 227, 187, 128, 144, 22, 242, 152, 29, 35, 126, 10, 196, 105, 236, 124, 143, 23, 209, 9, 167, 91, 231, 172, 164, 41, 164, 191, 18, 219, 120, 246, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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