Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0faaefaac4d2f1b4346b430c07a2a25be57d90c7602f783259fff1d6615eeecc

Tx prefix hash: 4a6a516b101bc8be7f7da47b9d6d2b98eff352eba7a4a7878643c6c1acd806b1
Tx public key: 2b9755bb6e80e4e14b45d0ae0a15dae317fca4d19ece709210009d117da3b43e
Timestamp: 1579672280 Timestamp [UTC]: 2020-01-22 05:51:20 Age [y:d:h:m:s]: 06:119:11:59:51
Block: 50656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1487759 RingCT/type: yes/0
Extra: 012b9755bb6e80e4e14b45d0ae0a15dae317fca4d19ece709210009d117da3b43e02110000000217786bcf000000000000000000

1 output(s) for total of 0.417019608007 xmr

stealth address amount amount idx tag
00: 9ebc2dd211c1c21c3a4f11b148a70c593ddec97a58b1328c582231b78bfe463a 0.417019608007 93928 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": 50666, "vin": [ { "gen": { "height": 50656 } } ], "vout": [ { "amount": 417019608007, "target": { "key": "9ebc2dd211c1c21c3a4f11b148a70c593ddec97a58b1328c582231b78bfe463a" } } ], "extra": [ 1, 43, 151, 85, 187, 110, 128, 228, 225, 75, 69, 208, 174, 10, 21, 218, 227, 23, 252, 164, 209, 158, 206, 112, 146, 16, 0, 157, 17, 125, 163, 180, 62, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 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: