Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 279045f5a403fe26ad2d697721216c5dc8d5d183eceddbe41ab9ecc4cbf31938

Tx prefix hash: b8bdf6f7c1239eb4f20cee9c3ee8c65a38d0395302922683a962aeba2d3491aa
Tx public key: 65e1469752f719cda8de17711b40b2707196598cf50e69c5bc50fa973f8ce34c
Timestamp: 1775246848 Timestamp [UTC]: 2026-04-03 20:07:28 Age [y:d:h:m:s]: 00:225:18:05:53
Block: 1512175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166771 RingCT/type: yes/0
Extra: 0165e1469752f719cda8de17711b40b2707196598cf50e69c5bc50fa973f8ce34c021100000019ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9edd50bf3f1b1dda023225752ac9df2d7f16fe833f1ce5cd748a78973d9ed34e 0.000600000000 2001973 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": 1512185, "vin": [ { "gen": { "height": 1512175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9edd50bf3f1b1dda023225752ac9df2d7f16fe833f1ce5cd748a78973d9ed34e" } } ], "extra": [ 1, 101, 225, 70, 151, 82, 247, 25, 205, 168, 222, 23, 113, 27, 64, 178, 112, 113, 150, 89, 140, 245, 14, 105, 197, 188, 80, 250, 151, 63, 140, 227, 76, 2, 17, 0, 0, 0, 25, 238, 75, 113, 129, 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: