Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3da400ec633a863694dbf62307c7f860c146283d97dbd60ec53f55f636ac113

Tx prefix hash: 4e8b63579c50f88c69dca85e1c957f20e274ee39599a8177b794e955af873570
Tx public key: 7a2825547c8fb9fb8834f5673ca020aaeffbfa212a27c1c1b76799e522adf6c5
Timestamp: 1739096131 Timestamp [UTC]: 2025-02-09 10:15:31 Age [y:d:h:m:s]: 01:284:09:10:51
Block: 1215435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467460 RingCT/type: yes/0
Extra: 017a2825547c8fb9fb8834f5673ca020aaeffbfa212a27c1c1b76799e522adf6c5021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2e91ef6df2c2d96231a068562c8fa9fc05a75d0b8e2667458f55b2b8e353f5f3 0.000600000000 1702234 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": 1215445, "vin": [ { "gen": { "height": 1215435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e91ef6df2c2d96231a068562c8fa9fc05a75d0b8e2667458f55b2b8e353f5f3" } } ], "extra": [ 1, 122, 40, 37, 84, 124, 143, 185, 251, 136, 52, 245, 103, 60, 160, 32, 170, 239, 251, 250, 33, 42, 39, 193, 193, 183, 103, 153, 229, 34, 173, 246, 197, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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: