Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561e6474f0d3f770af97ff7a3eea8d2f892f43a62378bbb721db7d8fdc79788f

Tx prefix hash: 37540249bd9f020e3cc3ddad45760ab549eb8561ea5574c37b29539fc35eff15
Tx public key: 8e133e47a78541b9c3eaec4620f84e3b3d36509fcf03112fac28d65321e6122a
Timestamp: 1576133205 Timestamp [UTC]: 2019-12-12 06:46:45 Age [y:d:h:m:s]: 06:069:07:30:42
Block: 26026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1453790 RingCT/type: yes/0
Extra: 018e133e47a78541b9c3eaec4620f84e3b3d36509fcf03112fac28d65321e6122a0211000000099159db1e000000000000000000

1 output(s) for total of 0.503229307746 xmr

stealth address amount amount idx tag
00: f93c1418a9be302e164055d28c34a08846ddd5d6d732a8b0f127aade0e4db7c6 0.503229307746 42977 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": 26036, "vin": [ { "gen": { "height": 26026 } } ], "vout": [ { "amount": 503229307746, "target": { "key": "f93c1418a9be302e164055d28c34a08846ddd5d6d732a8b0f127aade0e4db7c6" } } ], "extra": [ 1, 142, 19, 62, 71, 167, 133, 65, 185, 195, 234, 236, 70, 32, 248, 78, 59, 61, 54, 80, 159, 207, 3, 17, 47, 172, 40, 214, 83, 33, 230, 18, 42, 2, 17, 0, 0, 0, 9, 145, 89, 219, 30, 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) | dinastycoin version: tesla-369