Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4c2f57dfe2b73f1a7cdab799a13de477f34e3df8b4bd9507850319b38b61619

Tx prefix hash: e0cddcf9c85550fa2e4069b0f61ad2d77ac826b8ff2fb7436cac46d8331c0353
Tx public key: edb4c274006537f441ff404ebc65b29b6dfb34581e841cf2d37fe4bf0119b90a
Timestamp: 1649870229 Timestamp [UTC]: 2022-04-13 17:17:09 Age [y:d:h:m:s]: 04:220:16:13:06
Block: 479434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1202356 RingCT/type: yes/0
Extra: 01edb4c274006537f441ff404ebc65b29b6dfb34581e841cf2d37fe4bf0119b90a021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.015828376467 xmr

stealth address amount amount idx tag
00: 96651f7c248ef7c811c95b862350a71b2a5d126b6bc17756796766e5c5e5033a 0.015828376467 900331 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 dinastycoin-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": 479444, "vin": [ { "gen": { "height": 479434 } } ], "vout": [ { "amount": 15828376467, "target": { "key": "96651f7c248ef7c811c95b862350a71b2a5d126b6bc17756796766e5c5e5033a" } } ], "extra": [ 1, 237, 180, 194, 116, 0, 101, 55, 244, 65, 255, 64, 78, 188, 101, 178, 155, 109, 251, 52, 88, 30, 132, 28, 242, 211, 127, 228, 191, 1, 25, 185, 10, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: