Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc0129f85ffd5018cdfa66230a178488948e2385e99585897dec751fcf3d3225

Tx prefix hash: 5b4fbc3568f519c1090000d55d7c366648d184d265bea712df793aeefd0bd45a
Tx public key: 4d6d2f8e1628807a3f9d272767dfa55385f865df039e149b4db3ee2912d45e4b
Timestamp: 1647569337 Timestamp [UTC]: 2022-03-18 02:08:57 Age [y:d:h:m:s]: 04:250:08:08:38
Block: 460789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1222705 RingCT/type: yes/0
Extra: 014d6d2f8e1628807a3f9d272767dfa55385f865df039e149b4db3ee2912d45e4b0211000000052e6b1fd5000000000000000000

1 output(s) for total of 0.018247989541 xmr

stealth address amount amount idx tag
00: a85562a5c9c7cf957cab7a099cb90541513907d19a5eeabb7a270d998fd3b091 0.018247989541 877876 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": 460799, "vin": [ { "gen": { "height": 460789 } } ], "vout": [ { "amount": 18247989541, "target": { "key": "a85562a5c9c7cf957cab7a099cb90541513907d19a5eeabb7a270d998fd3b091" } } ], "extra": [ 1, 77, 109, 47, 142, 22, 40, 128, 122, 63, 157, 39, 39, 103, 223, 165, 83, 133, 248, 101, 223, 3, 158, 20, 155, 77, 179, 238, 41, 18, 212, 94, 75, 2, 17, 0, 0, 0, 5, 46, 107, 31, 213, 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: