Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 899eebea7b955d17265eca6ee6128cd27a120db76b3ed7cb92daa2f0fae59538

Tx prefix hash: f5419690f5c21c8e08aa7afe37e30db3d22a7a6138d2a2f7d45ff447a3d3be93
Tx public key: 2481116411c34f44c7cdc9fdf63edc7e46f9475fe822b4e02a3b7c740618758b
Timestamp: 1775136515 Timestamp [UTC]: 2026-04-02 13:28:35 Age [y:d:h:m:s]: 00:230:17:38:49
Block: 1511254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170460 RingCT/type: yes/0
Extra: 012481116411c34f44c7cdc9fdf63edc7e46f9475fe822b4e02a3b7c740618758b02110000000443b50471000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b837a92c1d717e1b2b1a837261ed186a71d3c53384822a75497babea0d535ee4 0.000600000000 2001044 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": 1511264, "vin": [ { "gen": { "height": 1511254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b837a92c1d717e1b2b1a837261ed186a71d3c53384822a75497babea0d535ee4" } } ], "extra": [ 1, 36, 129, 17, 100, 17, 195, 79, 68, 199, 205, 201, 253, 246, 62, 220, 126, 70, 249, 71, 95, 232, 34, 180, 224, 42, 59, 124, 116, 6, 24, 117, 139, 2, 17, 0, 0, 0, 4, 67, 181, 4, 113, 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: