Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af70499d4369f8beb642b37c229f5a6643ad6cbf2d02cf9676c19f5009de9611

Tx prefix hash: f7d9fd9eea57d55ff5ebf2e4ed794f24d0af9d7986ccfb693246b211a6c56cbe
Tx public key: ac1f709e78b1827ebd105f8a327476b8a04d9ec1c268bd956e707bc39baa7818
Timestamp: 1671377753 Timestamp [UTC]: 2022-12-18 15:35:53 Age [y:d:h:m:s]: 03:337:02:05:30
Block: 655348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1026701 RingCT/type: yes/0
Extra: 01ac1f709e78b1827ebd105f8a327476b8a04d9ec1c268bd956e707bc39baa78180211000000037e406890000000000000000000

1 output(s) for total of 0.004135804551 xmr

stealth address amount amount idx tag
00: d2af9d61280e755b47e3e7e92fba4284528b30b499bf2e8308ad5d57c1ad654e 0.004135804551 1095901 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": 655358, "vin": [ { "gen": { "height": 655348 } } ], "vout": [ { "amount": 4135804551, "target": { "key": "d2af9d61280e755b47e3e7e92fba4284528b30b499bf2e8308ad5d57c1ad654e" } } ], "extra": [ 1, 172, 31, 112, 158, 120, 177, 130, 126, 189, 16, 95, 138, 50, 116, 118, 184, 160, 77, 158, 193, 194, 104, 189, 149, 110, 112, 123, 195, 155, 170, 120, 24, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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: