Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624b357c9a45f9a4780f3d746f9ed262bb5de3fde8558a7cca67839a72142a06

Tx prefix hash: aec510e722814524f45a31685911bf5d6e3bcd5dc44d47c48f88edffa50c1ff5
Tx public key: 39a9c4b2382b164930ee1f90e259ba68874e26c058ef65c7efc40c9fe95161d2
Timestamp: 1580722390 Timestamp [UTC]: 2020-02-03 09:33:10 Age [y:d:h:m:s]: 06:294:05:59:13
Block: 57857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1625637 RingCT/type: yes/0
Extra: 0139a9c4b2382b164930ee1f90e259ba68874e26c058ef65c7efc40c9fe95161d20211000000054ac5aa02000000000000000000

1 output(s) for total of 0.394733563684 xmr

stealth address amount amount idx tag
00: c238ab4e7eb7a662d2d16feacfe8d9cf8cd208cb155df1bfa64ea28046aa08af 0.394733563684 106975 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": 57867, "vin": [ { "gen": { "height": 57857 } } ], "vout": [ { "amount": 394733563684, "target": { "key": "c238ab4e7eb7a662d2d16feacfe8d9cf8cd208cb155df1bfa64ea28046aa08af" } } ], "extra": [ 1, 57, 169, 196, 178, 56, 43, 22, 73, 48, 238, 31, 144, 226, 89, 186, 104, 135, 78, 38, 192, 88, 239, 101, 199, 239, 196, 12, 159, 233, 81, 97, 210, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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: