Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 498263322801f5576cce01557673c957cfc98d083e8ea7e0e6e6137bba059bf2

Tx prefix hash: 64d6cacf56c0e8c4153560737ee2acbe4b2091731ed6fa3c7295f59426f9e44d
Tx public key: dcb64ca13843cae8c4ee4424790d31a6ed7e919a45f369a8cb1a4a1466286449
Timestamp: 1731779282 Timestamp [UTC]: 2024-11-16 17:48:02 Age [y:d:h:m:s]: 02:004:16:21:44
Block: 1155107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528235 RingCT/type: yes/0
Extra: 01dcb64ca13843cae8c4ee4424790d31a6ed7e919a45f369a8cb1a4a1466286449021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 830ee300922841445af44ea34519f1c03a9c80b12534ce56eecdf628900ca2e0 0.000600000000 1640722 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": 1155117, "vin": [ { "gen": { "height": 1155107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "830ee300922841445af44ea34519f1c03a9c80b12534ce56eecdf628900ca2e0" } } ], "extra": [ 1, 220, 182, 76, 161, 56, 67, 202, 232, 196, 238, 68, 36, 121, 13, 49, 166, 237, 126, 145, 154, 69, 243, 105, 168, 203, 26, 74, 20, 102, 40, 100, 73, 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: