Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7b83a559cb53d0582cc95b52923cd5dc8ab280fa0957f6d600f7d17d7aaf5b1

Tx prefix hash: 52da1173cbeeef0ff00497ad13dd1fbe90c9a0eebd8c6d2ee6104b2d55477bda
Tx public key: 821b0bf6612f6d6c4976466740b68a07fdfbcbd297f5dab6fa3432b1a53a8621
Timestamp: 1735950684 Timestamp [UTC]: 2025-01-04 00:31:24 Age [y:d:h:m:s]: 01:319:21:00:35
Block: 1189666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492507 RingCT/type: yes/0
Extra: 01821b0bf6612f6d6c4976466740b68a07fdfbcbd297f5dab6fa3432b1a53a862102110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 52202a588e15963ff2c8aaca1121788b7f63fd801159ba8f2502218516a1c01e 0.000600000000 1676177 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 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": 1189676, "vin": [ { "gen": { "height": 1189666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52202a588e15963ff2c8aaca1121788b7f63fd801159ba8f2502218516a1c01e" } } ], "extra": [ 1, 130, 27, 11, 246, 97, 47, 109, 108, 73, 118, 70, 103, 64, 182, 138, 7, 253, 251, 203, 210, 151, 245, 218, 182, 250, 52, 50, 177, 165, 58, 134, 33, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: