Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 272f9148c50debfb4316d734220547c01aadb8af31999475921356a4170b8320

Tx prefix hash: 6df96bfd0b46775db2f1d7dfbacd5970529894a2048fee0257077da91e30f90c
Tx public key: ec1fb9a8f61dde8f868a7d2f6f655e7ddd950e63c12fbc72db8c9c1441057c21
Timestamp: 1730995141 Timestamp [UCT]: 2024-11-07 15:59:01 Age [y:d:h:m:s]: 00:161:23:39:14
Block: 1148629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115609 RingCT/type: yes/0
Extra: 01ec1fb9a8f61dde8f868a7d2f6f655e7ddd950e63c12fbc72db8c9c1441057c210211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 765f47d1df4293036a7ad8bd7a5863bb9552f043751e3ab5eaf269b65a5b1ba8 0.600000000000 1633520 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": 1148639, "vin": [ { "gen": { "height": 1148629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "765f47d1df4293036a7ad8bd7a5863bb9552f043751e3ab5eaf269b65a5b1ba8" } } ], "extra": [ 1, 236, 31, 185, 168, 246, 29, 222, 143, 134, 138, 125, 47, 111, 101, 94, 125, 221, 149, 14, 99, 193, 47, 188, 114, 219, 140, 156, 20, 65, 5, 124, 33, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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