Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d313d90219bccf567f7d1b11e4771b9c6f10043bc7011d0cfc122517faf0f75

Tx prefix hash: 7cd6487a7edc1f9b58a5757a9cf177ab370be50eadc9c51d1d8aae5a676ed170
Tx public key: f196e35a3e15b874b695b64a2cbbcc05c7b4ac06335d26b1acc73e4ba8b96b8e
Timestamp: 1708068591 Timestamp [UTC]: 2024-02-16 07:29:51 Age [y:d:h:m:s]: 02:194:00:19:38
Block: 958625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 664118 RingCT/type: yes/0
Extra: 01f196e35a3e15b874b695b64a2cbbcc05c7b4ac06335d26b1acc73e4ba8b96b8e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 66ad49edfbc6a8400ee34c372c004f2570dcf64c4ebb1d1a7c63765bed998a6d 0.000600000000 1417984 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": 958635, "vin": [ { "gen": { "height": 958625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66ad49edfbc6a8400ee34c372c004f2570dcf64c4ebb1d1a7c63765bed998a6d" } } ], "extra": [ 1, 241, 150, 227, 90, 62, 21, 184, 116, 182, 149, 182, 74, 44, 187, 204, 5, 199, 180, 172, 6, 51, 93, 38, 177, 172, 199, 62, 75, 168, 185, 107, 142, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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: